MON-4136: set up the PrometheusPossibleNarrowSelectors alert#2554
Conversation
machine424
commented
Jan 8, 2025
machine424
commented
- I added CHANGELOG entry for this change.
- No user facing changes, so no entry in CHANGELOG was needed.
openshift-ci
Bot
added
the
do-not-merge/work-in-progress
openshift-ci
Bot
added
the
approved
machine424
force-pushed
the
smooth-prom3
branch
from
ee2edf7 to
5be7f04
Compare
machine424
force-pushed
the
smooth-prom3
branch
4 times, most recently
from
d1d66f8 to
95f4a41
Compare
machine424
changed the title
|
@machine424, |
|
@machine424, |
|
@machine424, |
|
@machine424, |
1 similar comment
|
@machine424, |
|
/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.19-e2e-rosa-sts-hypershift-ovn openshift/prometheus#227 openshift/cluster-kube-apiserver-operator#1784 openshift/cluster-openshift-apiserver-operator#611 openshift/cluster-authentication-operator#752 #2554 |
|
@machine424: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/50647e70-d3fb-11ef-84ae-020c1e634813-0 |
|
@machine424: This PR was included in a payload test run from #2554
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/50647e70-d3fb-11ef-84ae-020c1e634813-0 |
|
@machine424: This pull request references MON-4136 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.19.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/test ? |
|
@machine424: The following commands are available to trigger required jobs: The following commands are available to trigger optional jobs: Use DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
machine424
force-pushed
the
smooth-prom3
branch
from
70d40ce to
187d9d7
Compare
|
/retest |
|
/payload-with-prs 4.19 nightly blocking openshift/thanos#158 |
|
@machine424: trigger 12 job(s) of type blocking for the nightly release of OCP 4.19
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/64699ce0-f8ca-11ef-8da6-947ded54a337-0 |
|
/payload-with-prs 4.19 ci blocking openshift/thanos#158 |
|
@machine424: trigger 4 job(s) of type blocking for the ci release of OCP 4.19
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/6cd07de0-f8ca-11ef-87ff-500987415ff7-0 |
|
I should have waited a little longer Which doesn't ship v3 |
|
/payload-with-prs 4.19 ci blocking openshift/thanos#158 |
|
/payload-with-prs 4.19 nightly blocking openshift/thanos#158 |
|
@machine424: trigger 12 job(s) of type blocking for the nightly release of OCP 4.19
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/2d6e8b30-f8f5-11ef-86d5-fe8009f34d88-0 |
|
@machine424: trigger 4 job(s) of type blocking for the ci release of OCP 4.19
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/2940e710-f8f5-11ef-99e9-6a09560173d5-0 |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jan--f, machine424 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Yes, it's temp, once/If we decide to ship it, we'll take the time to add a runbook, let's see how it performs. |
|
/hold cancel |
openshift-ci
Bot
removed
the
do-not-merge/hold
|
@machine424: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
[ART PR BUILD NOTIFIER] Distgit: cluster-monitoring-operator |
5 participants
